Add agent config column and evidence records for workflow runs #3
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| id = Column(Integer, primary_key=True, autoincrement=True) | ||
| name = Column(String(255), nullable=False, unique=True, index=True) | ||
| domain = Column(String(255), nullable=True) | ||
| config_json = Column(JSON, nullable=False, default=dict) |
There was a problem hiding this comment.
The new Agent.config_json field is declared as non‑nullable JSON without providing any migration or hot‑fix to add it to existing databases. All queries against Agent now select agents.config_json, so any installation running a pre‑existing SQLite file will start raising OperationalError: no such column: agents.config_json on startup (the project’s Base.metadata.create_all() calls will create new tables but will not add columns to existing ones). Please add an ALTER TABLE migration similar to other hotfix migrations or gate use of the column until the schema is upgraded.
Useful? React with 👍 / 👎.
Summary
Testing
https://chatgpt.com/codex/tasks/task_e_6907136c6dbc83328ae3a8ddfc60e076